Subsystem firewalls

ABSTRACT

The disclosed technology is generally directed to firewalls. In one example of the technology, a first firewall is used such that communication is blocked from a first subsystem of a device upon boot of the device. The first firewall is enabled to be configured by secure code subsequent to boot such that code that is not secure code is prevented from configuring the first firewall. After configuration of the first firewall, based on the configuration, the first firewall is used to selectively allow the first subsystem access to the first memory based on ranges of addresses of the first memory configured as accessible to the first subsystem.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of U.S. patent application Ser. No.15/607,311, filed May. 26, 2017, entitled “SUBSYSTEM FIREWALLS”. Theentirety of this afore-mentioned application is incorporated herein byreference.

BACKGROUND

The Internet of Things (“IoT”) generally refers to a system of devicescapable of communicating over a network. The devices can includeeveryday objects such as toasters, coffee machines, thermostat systems,washers, dryers, lamps, automobiles, and the like. The networkcommunications can be used for device automation, data capture,providing alerts, personalization of settings, and numerous otherapplications.

SUMMARY OF THE DISCLOSURE

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

Briefly stated, the disclosed technology is generally directed toconfigurable firewalls between components of an integrated circuit (IC).In one example of the technology, a first firewall is used such thatcommunication from a first subsystem of a device is blocked upon boot ofthe device. The first firewall is enabled to be configured by securecode, subsequent to boot, such that protections in the first firewallhave the effect that code that is not secure code is prevented fromconfiguring the first firewall. After configuration of the firstfirewall, based on the configuration, the first firewall is used toselectively allow the first subsystem access to the first memory basedon ranges of addresses of the first memory configured as accessible tothe first subsystem.

In some examples of the disclosure, a multi-core microprocessor devicehas at least one memory for the multiple cores of the device, such as astatic random access memory (SRAM) and/or a flash memory. In someexamples, the device has a Secure World and a Normal World, and securityon the device has protections for some areas of the device such that theareas can be accessed by Secure World but not by Normal World. However,some examples also have portions of memory associated with a particularNormal World source that can be accessed by that Normal World source butnot by other Normal World sources.

For instance, in some examples, the device has two or moremicrocontrollers that provide input/output (IO) functions, where thesemicrocontrollers are in Normal World and have a lower level of trustthan other cores on the device. In some examples, each of thesemicrocontrollers has a portion of memory on the SRAM and/or the flashmemory that should be accessible to one of these microcontrollers butnot to the others. Each of these microcontrollers may be included in asubsystem. At each IO subsystem, when the subsystem is attempting anaccess to the SRAM, a firewall may be used to selectively allow accessto a particular range of addresses of the SRAM. In this way, each IOsubsystem is allowed access to a particular range of addressesconfigured allowable for the microcontroller and denied access toaddresses outside of the allowed range of addresses for themicrocontroller. In some examples, the firewall may provide similarselective access to a particular range of addresses in a flash memory.

The firewall may deny the IO subsystem any access when the device isinitially booted, to prevent an attack from accessing the memory untilthe firewall has been configured. Each time the device is booted, thefirewall can be configured. In some examples, secure code, e.g. codefrom Secure World, can configure the firewall, but other code isprevented from configuring the firewall. In some examples, the IOsubsystems are not part of the Secure World, and so the IO subsystemscannot configure their own firewalls; the configuration of the firewallsis external to the IO subsystem. The configuration may include anindication, for the firewall, as to which range of addresses of the SRAM(and/or the flash memory, and/or the peripherals) the IO subsystem hasaccess to. In some examples, after the firewall is configured, a stickylock bit is set, so that the configuration of the firewall is fixeduntil the device is rebooted.

Other aspects of and applications for the disclosed technology will beappreciated upon reading and understanding the attached figures anddescription.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive examples of the present disclosure aredescribed with reference to the following drawings. In the drawings,like reference numerals refer to like parts throughout the variousfigures unless otherwise specified. These drawings are not necessarilydrawn to scale.

For a better understanding of the present disclosure, reference will bemade to the following Detailed Description, which is to be read inassociation with the accompanying drawings, in which:

FIG. 1 is a block diagram illustrating one example of a suitableenvironment in which aspects of the technology may be employed;

FIG. 2 is a block diagram illustrating one example of a suitablecomputing device according to aspects of the disclosed technology;

FIG. 3 is a block diagram illustrating an example of a system for devicesecurity;

FIG. 4 is a block diagram illustrating an example of a device for devicesecurity; and

FIG. 5 is a diagram illustrating an example dataflow for a process fordevice security, in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

The following description provides specific details for a thoroughunderstanding of, and enabling description for, various examples of thetechnology. One skilled in the art will understand that the technologymay be practiced without many of these details. In some instances,well-known structures and functions have not been shown or described indetail to avoid unnecessarily obscuring the description of examples ofthe technology. It is intended that the terminology used in thisdisclosure be interpreted in its broadest reasonable manner, even thoughit is being used in conjunction with a detailed description of certainexamples of the technology. Although certain terms may be emphasizedbelow, any terminology intended to be interpreted in any restrictedmanner will be overtly and specifically defined as such in this DetailedDescription section. Throughout the specification and claims, thefollowing terms take at least the meanings explicitly associated herein,unless the context dictates otherwise. The meanings identified below donot necessarily limit the terms, but merely provide illustrativeexamples for the terms. For example, each of the terms “based on” and“based upon” is not exclusive, and is equivalent to the term “based, atleast in part, on”, and includes the option of being based on additionalfactors, some of which may not be described herein. As another example,the term “via” is not exclusive, and is equivalent to the term “via, atleast in part”, and includes the option of being via additional factors,some of which may not be described herein. The meaning of “in” includes“in” and “on.” The phrase “in one embodiment,” or “in one example,” asused herein does not necessarily refer to the same embodiment orexample, although it may. Use of particular textual numeric designatorsdoes not imply the existence of lesser-valued numerical designators. Forexample, reciting “a widget selected from the group consisting of athird foo and a fourth bar” would not itself imply that there are atleast three foo, nor that there are at least four bar, elements.References in the singular are made merely for clarity of reading andinclude plural references unless plural references are specificallyexcluded. The term “or” is an inclusive “or” operator unlessspecifically indicated otherwise. For example, the phrases “A or B”means “A, B, or A and B.” As used herein, the terms “component” and“system” are intended to encompass hardware, software, or variouscombinations of hardware and software. Thus, for example, a system orcomponent may be a process, a process executing on a computing device,the computing device, or a portion thereof.

Briefly stated, the disclosed technology is generally directed toconfigurable firewalls between components of an integrated circuit (IC).In one example of the technology, a first firewall is used such thatcommunication from a first subsystem of a device is blocked upon boot ofthe device. The first firewall is enabled to be configured by securecode, subsequent to boot, such that protections in the first firewallhave the effect that code that is not secure code is prevented fromconfiguring the first firewall. After configuration of the firstfirewall, based on the configuration, the first firewall is used toselectively allow the first subsystem access to the first memory basedon ranges of addresses of the first memory configured as accessible tothe first subsystem.

In some examples of the disclosure, a multi-core microprocessor devicehas at least one memory for the multiple cores of the device, such as astatic random access memory (SRAM) and/or a flash memory. In someexamples, the device has a secure world (Secure World) and a normalworld (Normal World), and security on the device has protections forsome areas of the device such that the areas can be accessed by SecureWorld but not by Normal World. However, some examples also have portionsof memory associated with a particular Normal World source that can beaccessed by that Normal World source but not by other Normal Worldsources.

For instance, in some examples, the device has two or moremicrocontrollers that provide input/output (IO) functions, where thesemicrocontrollers are in Normal World and have a lower level of trustthan other cores on the device. In some examples, each of thesemicrocontrollers has a portion of memory on the SRAM and/or the flashmemory that should be accessible to one of these microcontrollers butnot to the others. Each of these microcontrollers may be included in asubsystem. At each IO subsystem, when the subsystem is attempting anaccess to the SRAM, a firewall may be used to selectively allow accessto a particular range of addresses of the SRAM. In this way, each IOsubsystem is allowed access to a particular range of addressesconfigured allowable for the microcontroller and denied access toaddresses outside of the allowed range of addresses for themicrocontroller. In some examples, the firewall may provide similarselective access to a particular range of addresses in a flash memory.

The firewall may deny the IO subsystem any access when the device isinitially booted, to prevent an attack from accessing the memory untilthe firewall has been configured. Each time the device is booted, thefirewall can be configured. In some examples, secure code, e.g. codefrom Secure World, can configure the firewall, but other code isprevented from configuring the firewall. In some examples, the IOsubsystems are not part of the Secure World, and so the IO subsystemscannot configure their own firewalls; the configuration of the firewallsis external to the IO subsystem. The configuration may include anindication, for the firewall, as to which range of addresses of the SRAM(and/or the flash memory, and/or the peripherals) the IO subsystem hasaccess to. In some examples, after the firewall is configured, a stickylock bit is set, so that the configuration of the firewall is fixeduntil the device is rebooted.

Illustrative Devices/Operating Environments

FIG. 1 is a diagram of environment 100 in which aspects of thetechnology may be practiced. As shown, environment 100 includescomputing devices 110, as well as network nodes 120, connected vianetwork 130. Even though particular components of environment 100 areshown in FIG. 1, in other examples, environment 100 can also includeadditional and/or different components. For example, in certainexamples, the environment 100 can also include network storage devices,maintenance managers, and/or other suitable components (not shown).Computing devices 110 shown in FIG. 1 may be in various locations,including on premise, in the cloud, or the like. For example, computerdevices 110 may be on the client side, on the server side, or the like.

As shown in FIG. 1, network 130 can include one or more network nodes120 that interconnect multiple computing devices 110, and connectcomputing devices 110 to external network 140, e.g., the Internet or anintranet. For example, network nodes 120 may include switches, routers,hubs, network controllers, or other network elements. In certainexamples, computing devices 110 can be organized into racks, actionzones, groups, sets, or other suitable divisions. For example, in theillustrated example, computing devices 110 are grouped into three hostsets identified individually as first, second, and third host sets 112a-112 c. In the illustrated example, each of host sets 112 a-112 c isoperatively coupled to a corresponding network node 120 a-120 c,respectively, which are commonly referred to as “top-of-rack” or “TOR”network nodes. TOR network nodes 120 a-120 c can then be operativelycoupled to additional network nodes 120 to form a computer network in ahierarchical, flat, mesh, or other suitable types of topology thatallows communications between computing devices 110 and external network140. In other examples, multiple host sets 112 a-112 c may share asingle network node 120. Computing devices 110 may be virtually any typeof general- or specific-purpose computing device. For example, thesecomputing devices may be user devices such as desktop computers, laptopcomputers, tablet computers, display devices, cameras, printers, orsmartphones. However, in a data center environment, these computingdevices may be server devices such as application server computers,virtual computing host computers, or file server computers. Moreover,computing devices 110 may be individually configured to providecomputing, storage, and/or other suitable computing services.

In some examples, one or more of the computing devices 110 is an IoTdevice, a device that comprises part or all of an IoT support service, adevice comprising part or all of an application back-end, or the like,as discussed in greater detail below.

Illustrative Computing Device

FIG. 2 is a diagram illustrating one example of computing device 200 inwhich aspects of the technology may be practiced. Computing device 200may be virtually any type of general- or specific-purpose computingdevice. For example, computing device 200 may be a user device such as adesktop computer, a laptop computer, a tablet computer, a displaydevice, a camera, a printer, or a smartphone. Likewise, computing device200 may also be server device such as an application server computer, avirtual computing host computer, or a file server computer, e.g.,computing device 200 may be an example of computing device 110 ornetwork node 120 of FIG. 1. Computing device 200 may also be an IoTdevice that connects to a network to receive IoT services. Likewise,computer device 200 may be an example any of the devices illustrated inor referred to in FIGS. 3-5, as discussed in greater detail below. Asillustrated in FIG. 2, computing device 200 includes processing circuit210, operating memory 220, memory controller 230, data storage memory250, input interface 260, output interface 270, and network adapter 280.Each of these afore-listed components of computing device 200 includesat least one hardware element.

Computing device 200 includes at least one processing circuit 210configured to execute instructions, such as instructions forimplementing the herein-described workloads, processes, or technology.Processing circuit 210 may include a microprocessor, a microcontroller,a graphics processor, a coprocessor, a field-programmable gate array, aprogrammable logic device, a signal processor, or any other circuitsuitable for processing data. Processing circuit 210 is an example of acore. The aforementioned instructions, along with other data (e.g.,datasets, metadata, operating system instructions, etc.), may be storedin operating memory 220 during run-time of computing device 200.Operating memory 220 may also include any of a variety of data storagedevices/components, such as volatile memories, semi-volatile memories,random access memories, static memories, caches, buffers, or other mediaused to store run-time information. In one example, operating memory 220does not retain information when computing device 200 is powered off.Rather, computing device 200 may be configured to transfer instructionsfrom a non-volatile data storage component (e.g., data storage component250) to operating memory 220 as part of a booting or other loadingprocess. In some examples, other forms of execution may be employed,such as execution directly from data storage component 250, e.g.,eXecute In Place (XIP).

Operating memory 220 may include 4^(th) generation double data rate(DDR4) memory, 3rd generation double data rate (DDR3) memory, otherdynamic random access memory (DRAM), High Bandwidth Memory (HBM), HybridMemory Cube memory, 3D-stacked memory, static random access memory(SRAM), magnetoresistive random access memory (MRAM), pseudorandomrandom access memory (PSRAM), or other memory, and such memory maycomprise one or more memory circuits integrated onto a DIMM, SIMM,SODIMM, Known Good Die (KGD), or other packaging. Such operating memorymodules or devices may be organized according to channels, ranks, andbanks. For example, operating memory devices may be coupled toprocessing circuit 210 via memory controller 230 in channels. Oneexample of computing device 200 may include one or two DIMMs perchannel, with one or two ranks per channel. Operating memory within arank may operate with a shared clock, and shared address and commandbus. Also, an operating memory device may be organized into severalbanks where a bank can be thought of as an array addressed by row andcolumn. Based on such an organization of operating memory, physicaladdresses within the operating memory may be referred to by a tuple ofchannel, rank, bank, row, and column.

Despite the above-discussion, operating memory 220 specifically does notinclude or encompass communications media, any communications medium, orany signals per se.

Memory controller 230 is configured to interface processing circuit 210to operating memory 220. For example, memory controller 230 may beconfigured to interface commands, addresses, and data between operatingmemory 220 and processing circuit 210. Memory controller 230 may also beconfigured to abstract or otherwise manage certain aspects of memorymanagement from or for processing circuit 210. Although memorycontroller 230 is illustrated as single memory controller separate fromprocessing circuit 210, in other examples, multiple memory controllersmay be employed, memory controller(s) may be integrated with operatingmemory 220, or the like. Further, memory controller(s) may be integratedinto processing circuit 210. These and other variations are possible.

In computing device 200, data storage memory 250, input interface 260,output interface 270, and network adapter 280 are interfaced toprocessing circuit 210 by bus 240. Although, FIG. 2 illustrates bus 240as a single passive bus, other configurations, such as a collection ofbuses, a collection of point to point links, an input/output controller,a bridge, other interface circuitry, or any collection thereof may alsobe suitably employed for interfacing data storage memory 250, inputinterface 260, ouput interface 270, or network adapter 280 to processingcircuit 210.

In computing device 200, data storage memory 250 is employed forlong-term non-volatile data storage. Data storage memory 250 may includeany of a variety of non-volatile data storage devices/components, suchas non-volatile memories, disks, disk drives, hard drives, solid-statedrives, or any other media that can be used for the non-volatile storageof information. However, data storage memory 250 specifically does notinclude or encompass communications media, any communications medium, orany signals per se. In contrast to operating memory 220, data storagememory 250 is employed by computing device 200 for non-volatilelong-term data storage, instead of for run-time data storage.

Also, computing device 200 may include or be coupled to any type ofprocessor-readable media such as processor-readable storage media (e.g.,operating memory 220 and data storage memory 250) and communicationmedia (e.g., communication signals and radio waves). While the termprocessor-readable storage media includes operating memory 220 and datastorage memory 250, the term “processor-readable storage media,”throughout the specification and the claims whether used in the singularor the plural, is defined herein so that the term “processor-readablestorage media” specifically excludes and does not encompasscommunications media, any communications medium, or any signals per se.However, the term “processor-readable storage media” does encompassprocessor cache, Random Access Memory (RAM), register memory, and/or thelike.

Computing device 200 also includes input interface 260, which may beconfigured to enable computing device 200 to receive input from users orfrom other devices. In addition, computing device 200 includes outputinterface 270, which may be configured to provide output from computingdevice 200. In one example, output interface 270 includes a framebuffer, graphics processor, graphics processor or accelerator, and isconfigured to render displays for presentation on a separate visualdisplay device (such as a monitor, projector, virtual computing clientcomputer, etc.). In another example, output interface 270 includes avisual display device and is configured to render and present displaysfor viewing. In yet another example, input interface 260 and/or outputinterface 270 may include a universal asynchronous receiver/transmitter(“UART”), a Serial Peripheral Interface (“SPI”), Inter-IntegratedCircuit (“I2C”), a General-purpose input/output (GPIO), and/or the like.Moreover, input interface 260 and/or output interface 270 may include orbe interfaced to any number or type of peripherals.

In the illustrated example, computing device 200 is configured tocommunicate with other computing devices or entities via network adapter280. Network adapter 280 may include a wired network adapter, e.g., anEthernet adapter, a Token Ring adapter, or a Digital Subscriber Line(DSL) adapter. Network adapter 28 o may also include a wireless networkadapter, for example, a Wi-Fi adapter, a Bluetooth adapter, a ZigBeeadapter, a Long Term Evolution (LTE) adapter, SigFox, LoRa, Powerline,or a 5G adapter.

Although computing device 200 is illustrated with certain componentsconfigured in a particular arrangement, these components and arrangementare merely one example of a computing device in which the technology maybe employed. In other examples, data storage memory 250, input interface260, output interface 270, or network adapter 280 may be directlycoupled to processing circuit 210, or be coupled to processing circuit210 via an input/output controller, a bridge, or other interfacecircuitry. Other variations of the technology are possible.

Some examples of computing device 200 include at least one memory (e.g.,operating memory 220) adapted to store run-time data and at least oneprocessor (e.g., processing unit 210) that is adapted to executeprocessor-executable code that, in response to execution, enablescomputing device 200 to perform actions.

Illustrative Systems

FIG. 3 is a block diagram illustrating an example of a system (300) fordevice security. System 300 may include network 330, as well as IoTsupport service 351, IoT devices 341 and 342, and application back-end313, which all connect to network 330.

The term “IoT device” refers to a device intended to make use of IoTservices. An IoT device can include virtually any device that connectsto a network to use IoT services, including for telemetry collection orany other purpose. IoT devices include any devices that can connect to anetwork to make use of IoT services. In various examples, IoT devicesmay communicate with a cloud, with peers or local system or acombination or peers and local systems and the cloud, or in any othersuitable manner. IoT devices can include everyday objects such astoasters, coffee machines, thermostat systems, washers, dryers, lamps,automobiles, and the like. IoT devices may also include, for example, avariety of devices in a “smart” building including lights, temperaturesensors, humidity sensors, occupancy sensors, and the like. The IoTservices for the IoT devices can be used for device automation, datacapture, providing alerts, personalization of settings, and numerousother applications.

The term “IoT support service” refers to a device, a portion of at leastone device, or multiple devices such as a distributed system, to which,in some examples, IoT devices connect on the network for IoT services.In some examples, the IoT support service is an IoT hub. In someexamples, the IoT hub is excluded, and IoT devices communicate with anapplication back-end, directly or through one or more intermediaries,without including an IoT hub, and a software component in theapplication back-end operates as the IoT support service. IoT devicesreceive IoT services via communication with the IoT support service. Insome examples, an IoT support service may be embedded inside of adevice, or in local infrastructure.

Application back-end 313 refers to a device, or multiple devices such asa distributed system, that performs actions that enable data collection,storage, and/or actions to be taken based on the IoT data, includinguser access and control, data analysis, data display, control of datastorage, automatic actions taken based on the IoT data, and/or the like.Application back-end 313 could also be one or more virtual machinesdeployed in a public or a private cloud. In some examples, at least someof the actions taken by the application back-end may be performed byapplications running in application back-end 313.

Each of the IoT devices 341 and 342 and/or the devices that comprise IoTsupport service 351 and/or application back-end 313 may include examplesof computing device 200 of FIG. 2. The term “IoT support service” is notlimited to one particular type of IoT service, but refers to the deviceto which the IoT device communicates, after provisioning, for at leastone IoT solution or IoT service. That is, the term “IoT supportservice,” as used throughout the specification and the claims, isgeneric to any IoT solution. The term IoT support service simply refersto the portion of the IoT solution/IoT service to which provisioned IoTdevices communicate. In some examples, communication between IoT devicesand one or more application back-ends occur with an IoT support serviceas an intermediary. FIG. 3 and the corresponding description of FIG. 3in the specification illustrates an example system for illustrativepurposes that does not limit the scope of the disclosure.

One or more of the IoT devices 341 and 342 may include device controller345, which may operate to control the IoT device. Each device controller345 may include multiple execution environments. Device controller 345may be a multi-core microcontroller. In some examples, device controller345 is an integrated circuit with multiple cores, such as at least onecentral processing unit (CPU) and at least one microcontroller (MCU).

Network 330 may include one or more computer networks, including wiredand/or wireless networks, where each network may be, for example, awireless network, local area network (LAN), a wide-area network (WAN),and/or a global network such as the Internet. On an interconnected setof LANs, including those based on differing architectures and protocols,a router acts as a link between LANs, enabling messages to be sent fromone to another. Also, communication links within LANs typically includetwisted wire pair or coaxial cable, while communication links betweennetworks may utilize analog telephone lines, full or fractionaldedicated digital lines including T1, T2, T3, and T4, IntegratedServices Digital Networks (ISDNs), Digital Subscriber Lines (DSLs),wireless links including satellite links, or other communications linksknown to those skilled in the art. Furthermore, remote computers andother related electronic devices could be remotely connected to eitherLANs or WANs via a modem and temporary telephone link. Network 330 mayinclude various other networks such as one or more networks using localnetwork protocols such as 6LoWPAN, ZigBee, or the like. Some IoT devicesmay be connected to a user device via a different network in network 330than other IoT devices. In essence, network 330 includes anycommunication method by which information may travel between IoT supportservice 351, IoT devices 341 and 342, and application back-end 313.Although each device or service is shown connected as connected tonetwork 330, that does not mean that each device communicates with eachother device shown. In some examples, some devices/services shown onlycommunicate with some other devices/services shown via one or moreintermediary devices. Also, although network 330 is illustrated as onenetwork, in some examples, network 330 may instead include multiplenetworks that may or may not be connected with each other, with some ofthe devices shown communicating with each other through one network ofthe multiple networks and other of the devices shown communicating witheach other with a different network of the multiple networks.

As one example, IoT devices 341 and 342 are devices that are intended tomake use of IoT services provided by IoT support service 351.

System 300 may include more or less devices than illustrated in FIG. 3,which is shown by way of example only.

Illustrative Device

FIG. 4 is a block diagram illustrating an example of device controller445. Device controller 445 may be employed as an example of devicecontroller 345 of FIG. 3. Device controller 445 may include securitycomplex 451, CPU 453, direct memory access (DMA) block 454, trust zone(TZ) DMA block 455, Flash memory 456, Radio block 457, secure staticrandom access memory (SRAM) 458, Input/Output (IO) Subsystem 481, IOSubsystem 482, primary advanced extensible interface (AXI) bus 463,secondary AXI bus 464, bridges 465 and 466, AXI to advanced peripheralbus (APB) bridges per peripheral 467, Interfaces 471, general purposeIOs (GPIOs) 472, analog-to-digital converter (ADC) 473, real-time clock(RTC) 474, and performance counter 475. IO subsystem 481 may include MCU461, and IO subsystem 482 may include MCU 462. In some examples, many ofthe components have firewalls, as illustrated in FIG. 4. In particular,in some examples, IO subsystem 481 has firewall 491, and IO subsystem482 has firewall 492.

FIG. 4 illustrates but one non-limiting example of device controller 445and one particular layout of the AXI, AHB, and APB for exemplarypurposes. Other suitable layouts and examples of device controller 445may also be employed.

In some examples, device controller 445 enables a device in which devicecontroller 445 is included to operate as an IoT device, such as IoTdevice 341 or 342 of FIG. 3. In some examples, device controller 445 isa multi-core microcontroller. In some examples, device controller 445runs a high-level operating system. In some examples, device controller445 may have at least 4 MB of RAM and at least 4 MB of flash memory, andmay be a single integrated circuit. In some examples, device controller445 provides not just network connectivity, but various other functionsincluding hardware and software security, a monitored operating system,cryptographic functions, peripheral control, telemetry, and/or the like.In addition, device controller 445 may include technology for allowingdevice controller 445 to be booted in a secure manner, allowing devicecontroller 445 to be securely updated, ensuring that proper software isrunning on device controller 445, allowing device controller 445 tofunction correctly as an IoT device, and/or the like.

In some examples, security complex 451 includes a core security complex(CSC) that is the hardware root of trust in device controller 445. Insome examples, the core security complex is directly connected to thesecure MCU in security complex 451. In some examples, the secure MCU insecurity complex 451 has a very high degree of trust, but is lesstrusted than the core security complex in security complex 451. In someexamples, security complex 451 brings up the full system at boot.

In some examples, CPU 453 runs a high-level operating system. In someexamples, CPU 453 has two independent execution environments: a secureworld (Secure World) execution environment and a normal world (NormalWorld) execution environment. The term “secure world” is used broadly torefer to a trusted environment and is not limited to a particularsecurity feature. In some examples, the Secure World executionenvironment of CPU 453 is also part of the trusted computing base of thesystem. For instance, in some examples, the Secure World executionenvironment of CPU 453 has unfettered access to reprogram hardwareprotection mechanisms, such as firewalls in some examples. In someexamples, the Secure World execution environment of CPU 453 does not,however, have access to the internals of the core security complex ofsecurity complex 451 and relies on the secure MCU of security complex451 for particular security-sensitive operations. In some examples, theSecure World of CPU 453 and security complex 451 are the Secure World ofdevice 445 which executes secure code, and the rest of device controller445 is the Normal World of device 445 which does not execute securecode.

Radio block 457 may provide Wi-Fi communication. Primary AXI bus 463 andsecondary bus AXI 464 may be buses that connect the components shown. Insome examples, bridges 465, 466, and 467 bridge the components shown.RTC block 474 may operate as a real-time clock. In some examples, allcomponents in device controller 345 can read from the RTC block 474, butnot all components have write access to RTC block 474. Device controller445 may include various forms of memory, including flash and SRAM, suchas flash memory 456 and secure SRAM 458.

In some examples, IO subsystem 481 and IO subsystem 482 are I/Osubsystems for general purpose I/O connectivity. In some examples, IOsubsystem 481 and IO subsystem 482 each include an MCU-MCU 461 and MCU462 respectively in the example illustrated in FIG. 4.

DMA block 454 may be used to manage data movement for the Normal Worldexecution environment of CPU 453. Trust zone (TZ) DMA block 455 may beused to manage data movement for the Secure World execution environmentof CPU 453. In some examples, each IO subsystem also has its own DMAblock/engine. Each of the DMA blocks/engines may be configured tosupport data movement between cores, peripherals, other components,and/or the like.

Each of the cores may have bi-directional mailboxes to supportinter-processor communication. Performance counter 475 may be configuredto count read requests, write requests, and data type requests forperformance monitoring. In some examples, performance counter 475 mayalso be configured to measure latency from a core to a target, such asfrom MCU 462 to SRAM 458.

In some examples, the interfaces at block 459 include twoInter-integrated circuit Sound (I2S) interfaces: one for audio input andone for audio output. In other examples, other configurations ofinterfaces may be employed, and block 459 may include any suitableinterfaces in various examples.

In some examples, as explained in greater detail below, the independentexecution environments of device controller 445—which may include, forexample, each core in device controller 445, and in some cases multipleindependent execution environments within one core (e.g., the SecureWorld operating environment in CPU 453 and the Normal World operatingenvironment in CPU 453)—may operate within a hierarchy of trust. In someexamples, the hierarchy of trust may play a role in which peripheralsare assigned to particular cores. However, the disclosure is not solimited, and in other examples, there is no hierarchy of trust in devicecontroller 445 and the determinations as to which peripherals areassigned to particular cores are based on other factors.

In some examples, the MCU in security complex 451 has a very high degreeof trust, but is less trusted than the core security complex in securitycomplex 451. In these examples, the MCU in security complex 451 controlsone or more functions associated with a very high degree of trust. Inone example, the MCU in security complex 451 controls power for devicecontroller 445 and/or an IoT device.

In some examples, the Secure World execution environment of CPU 453 isalso part of the trusted computing base of the system. For instance, insome examples, the Secure World runtime of CPU 453 (Secure World RT) hasunfettered access to reprogram hardware protection mechanisms, such asfirewalls in some examples. In some examples, Secure World RT does not,however, have access to the internals of the core security complex ofsecurity complex 451 and relies on the MCU in security complex 451 forparticular security-sensitive operations.

The Normal World execution environment of CPU 453 may be configured tohave limited access to such on-chip resources such as memories. In someexamples, various security and quality standards (e.g., relatively highstandards) may be enforced for code running in this environment but isless trusted than either the code running on the MCU in security complex451 or the code running in the Secure World of CPU 453.

In some examples, MCUs 461 and 462 are less trusted than the MCU insecurity complex 451 and less trusted than CPU 453. In some examples,Radio block 457 may include a core, which may be an MCU in someexamples. Radio block 457 may provide Wi-Fi functionality andconnectivity to the Internet and cloud services such as IoT services. Insome examples, Radio block 457 may provide communications via Bluetooth,Near Field Communication (NFC), ZigBee, Long-Term Evolution (LTE),and/or other connectivity technology. In some examples, the core inRadio block 457 does not have any access to unencrypted secrets, and isnot capable of compromising the execution of CPU 453. In some examples,Radio block 457 is a slave to CPU 453. In general, FIG. 4 illustrateswhich components operate as slaves and which components operate asmasters.

In some examples, each independent execution environment is managed by asingle software component executing in a separate execution environmentthat is referred to the “parent” of the execution environment. In suchexamples, one exception may be that the hardware root of trust (the coresecurity complex of security complex 451 in this example) has no parent.In one particular example, each parent executes in an environment thatis at least as trusted as the environments it manages. In otherexamples, other suitable means of security may be employed. Managementoperations may include booting and resuming the target environment,monitoring and handling resets in the target environment, andconfiguring access policy for the target environment. In some cases,certain management operations are performed by a component other than aparent. For instance, in some examples, CPU Normal World is theenvironment that manages MCUs 461 and 462, but receives assistance fromthe Secure World of CPU 453 to do so.

For instance, in some examples, the MCU of security complex 451 managesSecure World RT of CPU 453, a component in Secure World RT in CPU 453manages Normal World OS of CPU 453, a component in the Normal World OSof CPU 453 manages Normal World user-mode of CPU 453, and Normal Worlduser-mode services of CPU 453 manages the MCUs 461 and 462 and the corein Radio block 457.

In some examples, not only are independent execution environmentsmanaged by a software component from a more trusted executionenvironment, but different functions are assigned to the differentindependent execution environments, with more sensitive functionsassigned to more trusted independent execution environments. In oneparticular example, independent execution environments less trusted thanthe independent execution environment to which it is assigned arerestricted from having access to the function. In this way, in someexamples, the independent execution environments achievedefense-in-depth based on a hierarchy of trust.

For instance, in some examples, the core security complex of securitycomplex 451 is at the top of the hierarchy and is assigned to secrets(e.g., encryption keys), the secure MCU in core security complex 451 isnext in the hierarchy and is assigned to controlling power, Secure WorldRT of CPU 453 is next in the hierarchy and is assigned to storage and towrite access to a real time clock (RTC), Normal World OS of CPU 453 isnext in the hierarchy and is assigned to Wi-Fi, Normal World user-modeapplications of CPU 453 is next in the hierarchy and is assigned toapplications, and the MCUs 461 and 462 are at the bottom of thehierarchy and are assigned to peripherals. In other examples, functionsare assigned to independent execution environments in a differentmanner.

In some examples, each level of the hierarchy of trust, except for thebottom (i.e., least trusted) level of the hierarchy, has control overaccepting or rejecting requests from a less trusted level, e.g., interms of implementing support for the software they handle, and have theability to rate limit or audit the requests from less trusted levels,and to validate requests from lower levels, e.g., to ensure that therequests correct and true. Also, as previously discussed, in someexamples, each level of hierarchy except the top (i.e., most trusted)level has a parent that is responsible for managing the lower (i.e.,less trusted) level, including monitoring whether the software on thelower level is running correctly.

In the example given above, MCUs 461 and 462 are assigned toperipherals. In these examples, MCUs 461 and 462 may be referred to asIO MCUs.

In some examples, each of the cores on device controller 445, such asthe MCU in security complex 451, CPU 453, MCU 461, and MCU 462 have aRAM for active memory, as well as one or more memories that may retaininformation at least until device 445 is powered off or rebooted. Insome examples, the cores share SRAM 458 and flash memory 456 as memoriesthat may maintain information at least until device 445 is powered offor rebooted, but not all cores have access to the entirety of SRAM 458and flash memory 456. In some examples, firewall 491 prevents improperaccess by IO subsystem 481, including improper access to SRAM 458 andflash memory 456. Similarly, in some examples, firewall 492 preventsimproper access by IO subsystem 482, including improper access to SRAM458 and flash memory 456.

First, in some examples, during normal operations, for certain secureregions of SRAM 458, the slave firewall on SRAM 458 allows access to thesecure regions to Secure World, but prevents access to the secureregions by Normal World. Similarly, in some examples, for certain secureregions of flash memory 456, the slave firewall of flash memory 456allows access to the secure region to Secure World, but prevents accessto the secure region by Normal World.

However, in some examples, firewalls 491 and 492 do not determine accessto particular regions based only on whether the source attempting accessis Secure World or not. For example, SRAM 458 may also have portions ofmemory associated with a particular Normal World source, IO subsystem 1,that, based on the configuration of firewalls 491 and 492, can beaccessed by that IO subsystem 1 but not by IO subsystem 2. Similarly,flash memory 456 may also have portions of memory associated with aparticular Normal World source, IO subsystem 481, that, based on theconfiguration of firewalls 491 and 492, can be accessed by that IOsubsystem 1 but not by IO subsystem 2.

For instance, in some examples, IO MCU 461 and IO MCU 462 each have aportion of memory on SRAM 458 and each have a portion of memory on flashmemory 456. In some examples, the portion of SRAM 458 for IO MCU 461should be accessible to IO MCU 461 but not to IO MCU 462. Similarly, insome examples, via firewall 492, the portion of flash memory 456 for IOMCU 462 should be accessible to IO MCU 462 but not to IO MCU 461.

As discussed in greater detail below, firewall 491 may also selectivelyblock particular types of access to a particular region, such as readaccess, write access, and/or execute access.

During normal operations, in some examples, IO subsystem 481 and IOsubsystem 482 are each prevented from improper communications by amemory protection unit (MPU). However, in some examples, the MPUs aresoftware running in Normal World and are not trusted, and it is possiblefor malicious code stop the MPU from preventing improper communications.

In some examples, firewall 491 is a master hardware firewall that isprevented from being configured by code that is not secure code, wherefirewall 491 prevents improper communication from IO subsystem 481. Insome examples, the term “master firewall” refers to the fact that, forexample, IO subsystem 481 is a master while peripherals, SRAM 458, andflash memory 456 are slaves. In some examples, firewalls at aperipheral, at SRAM 458, and at flash memory 456 are slave firewalls,whereas the firewall at IO subsystem 481 is a master firewall.

Similarly, in some examples, firewall 492 is a master hardware firewallthat is prevented from being configured by code that is not secure code,where firewall 492 prevents improper communication from IO subsystem481. In some examples, during normal operation, firewall 491 allows IOsubsystem 481 access to some portions of SRAM 458, to some portions offlash memory 456, and to some peripherals, but prevents any othercommunication from leaving IO subsystem 481. Similarly, in someexamples, during normal operation, firewall 492 allows IO subsystem 482access to some portions of SRAM 458, to some portions of flash memory456, and to some peripherals, but prevents any other communication fromleaving IO subsystem 482.

In some examples, firewall 491 is a master hardware firewall thateffectively gives IO subsystem 481 hardware isolation from the rest ofdevice controller 445, and communication not specifically allowed byhardware firewall 491 is prevented from leaving IO subsystem 481, andcode that is not secure code from a source external to IO subsystem 481is prevented from configuring firewall 491. In some examples, firewall492 may provide similar hardware isolation to IO subsystem 482.

In some examples, during normal operation, for a request for access toSRAM 458 from IO subsystem 481, firewall 491 selectively allows IOsubsystem 481 access to a particular window of SRAM 458 that isconfigured allowable in firewall 491 and where this window of SRAM 458acts as the portion of SRAM 458 that is memory for MCU 461. In someexamples, the window of SRAM 458 that is configured allowable infirewall 491 is a particular range of addresses in SRAM 458. Similarly,in some examples, during normal operation, for a request for access toSRAM 458 from IO subsystem 482, firewall 492 selectively allows IOsubsystem 482 access to a particular range of addresses configuredallowable in firewall 492 and where this particular range of addressesacts as the portion of SRAM 456 that is memory for MCU 462. In someexamples, the range of addresses of SRAM 456 configured allowable infirewall 492 for IO subsystem 482 is separate and non-overlapping withthe range of addresses of SRAM 456 configured allowable in firewall 491for IO subsystem 481. In some examples, at least a portion of the rangeof addresses of SRAM 456 configured allowable in firewall 492 for IOsubsystem 482 is at least partially non-overlapping with the range ofaddresses of SRAM 456 configured allowable in firewall 491 for IOsubsystem 481.

Similarly, in some examples, during normal operation, for a request foraccess to flash memory 456 from IO subsystem 481, firewall 491selectively allows IO subsystem 481 access to a particular range ofaddresses configured allowable in firewall 491 and where this particularrange of addresses acts as the portion of flash memory 456 that ismemory for MCU 461. Similarly, in some examples, during normaloperation, for a request for access to SRAM 458 from IO subsystem 482,firewall 492 selectively allows IO subsystem 482 access to a particularrange of addresses configured allowable in firewall 492 and where thisparticular range of addresses acts as the portion of flash memory 458that is memory for MCU 462.

In some examples, firewalls 491 and 492 are dynamically configurablehardware firewalls. In some examples, firewalls 491 and firewall 492 areconfigurable and can be configured again each time device controller 445is booted. In some examples, upon boot of device controller 445,firewall 491 denies all communication to and from IO subsystem 481 untilfirewall 491 is properly configured, and firewall 492 denies allcommunication to and from IO subsystem 482 until firewall 492 isproperly configured. In some examples, firewalls 491 and 492 can beconfigured by secure code, and are prevented from being configured bycode that is not secure code.

The configuration of firewall 491 may include, for examples,configurations as to which range of addresses the IO subsystem 481 hasaccess to for requests for access to SRAM 458 and/or flash memory 456,as well as configurations as to which peripherals IO subsystem 481 hasaccess to. Similarly, the configuration of firewall 492 may include, forexamples, configurations as to which range of addresses the IO subsystem482 has access to for requests for access to SRAM 458 and/or flashmemory 456, as well as configurations as to which peripherals IOsubsystem 482 has access to.

Firewalls 491 and 492 may each include a sticky lock bit. For firewall491 and firewall 492, the sticky lock bit may be set, so theconfiguration for the firewall is fixed until device controller 445 isrebooted. “Sticky” bit as used herein means a bit that has two values,and once the bit is set, it is prevented from being changed until thedevice 445 reboots. For firewall 491 and firewall 492, the firewall maybe configured such the firewall is prevented from being changed whilethe sticky lock bit is set. That is, in some examples, once the stickylock bit is set, further writes to the firewall have may be ignored orotherwise ineffective. In some examples, firewall 491 is dynamicallyreconfigurable until its sticky lock bit is set, and firewall 492 isdynamically reconfigurable until its sticky lock bit is set.

During normal operation, after firewalls have been configured and thesticky lock bits have been set, the firewalls may then be used asconfigured. After configuration, in some examples, when access to SRAM458 is requested by IO subsystem 481, firewall 491 selectively grantsaccess. In some examples, firewall 491 determines the address rangeconfigured for access to SRAM 458 by IO subsystem 481, and determineswhether to grant access based on whether the address of the request isincluded in the address range. In some examples, if so, the request isgranted, and if not, the request is denied.

Similarly, in some examples after configuration, when access to flashmemory 456 is requested by IO subsystem 481, firewall 491 selectivelygrants access. In some examples, firewall 491 determines the addressrange configured for access to flash memory 456 by IO subsystem 481, anddetermines whether to grants access based on whether address of therequest is included in the address range. In some examples, if so, therequest is granted, and if not, the request is denied.

Similarly, after configuration, in some examples, when communicationwith a peripheral is requested by IO subsystem 481, firewall 491selectively grants access. In some examples, firewall 491 determineswhich peripherals IO subsystem 481 has access to based on theconfiguration, and determines whether the peripheral that IO subsystem481 is requesting to communicate with is one of the peripherals allowedfor IO subsystem 481 according to the configuration. In some examples,if so, the request is granted, and if not, the request is denied.

Similarly, after configuration, in some examples, when access to SRAM458 is requested by IO subsystem 482, firewall 492 selectively grantsaccess. In some examples, firewall 492 determines the address rangeconfigured for access to SRAM 458 by IO subsystem 482, and determinateswhether to grants access based on whether the address of the request isincluded in the address range. In some examples, if so, the request isgranted, and if not, the request is denied.

Similarly, after configuration, in some examples, when access to flashmemory 456 is requested by IO subsystem 482, firewall 492 selectivelygrants access. In some examples, firewall 491 determines the addressrange configured for access to flash memory 456 by IO subsystem 482, anddeterminates whether to grants access based on whether the address ofthe request is included in the address range. In some examples, if so,the request is granted, and if not, the request is denied.

Similarly, after configuration, in some examples, when communicationwith a peripheral is requested by IO subsystem 482, firewall 492selectively grants access. In some examples, firewall 492 determineswhich peripherals that IO subsystem 481 has access to based on theconfiguration, and determines whether the peripheral that IO subsystem481 is requesting to communicate with is one of the peripherals allowedfor IO subsystem 481 according to the configuration. In some examples,if so, the request is granted, and if not, the request is denied.

Configurations for firewalls 491 and 492 may also include type ofaccess. For example, firewall 491 may filter types of access requestsfrom IO subsystem 481 versus address range, as previously discussed, butalso may configure particular certain types of access for certainaddress ranges. For example, firewall 491 may prevent all execution, orexecution to particular addresses. As another example, firewall 491 mayuniversally prevent, or prevent to particular addresses, code fetches,but for certain address ranges data reads and data writes may beallowed, while not allowing IO subsystem 481 a code fetch from thoseaddresses. Firewall 492 may be configured in a similar way with regardto IO subsystem 481 in some examples.

Firewalls 491 may be configurable in the specific manners discussedabove. In some examples, configurations of firewalls 491 and 492 thatconfigures various access, such as access to particular ranges ofmemories and/or particular peripherals, do not persist upon devicereboot. Rather, in these examples, when the device is rebooted, thefirewalls 491 and 492 blocks all access, regardless of previousconfiguration of the firewall, and to not allow access again untilconfigured again subsequent to boot.

Although particular subsystems are discussed herein in conjunction theparticular subsystem firewalls, the disclosure is not so limited, andother suitable subsystems may be employed with corresponding mastersubsystem firewalls for the subsystems. For instance, while IOsubsystems have been discussed within, in other examples, the subsystemsare not IO subsystems.

In some examples, sticky lock bits are not used, and the firewalls areinstead dynamic and reconfigurable throughout operation. For instance,in some examples, SRAM 458 may use buffers and then release the buffers,so that the range of addresses that should be available to a subsystemmay dynamically change over time. In these examples, secure code may beable to reconfigure subsystem firewalls such as firewall 491 and 492over time to reflect the range of addresses that now reflect the memoryavailable to IO subsystem 481 and IO subsystem 482, respectively.

Illustrative Processes

For clarity, the processes described herein are described in terms ofoperations performed in particular sequences by particular devices orcomponents of a system. However, it is noted that other processes arenot limited to the stated sequences, devices, or components. Forexample, certain acts may be performed in different sequences, inparallel, omitted, or may be supplemented by additional acts orfeatures, whether or not such sequences, parallelisms, acts, or featuresare described herein. Likewise, any of the technology described in thisdisclosure may be incorporated into the described processes or otherprocesses, whether or not that technology is specifically described inconjunction with a process. The disclosed processes may also beperformed on or by other devices, components, or systems, whether or notsuch devices, components, or systems are described herein. Theseprocesses may also be embodied in a variety of ways. For example, theymay be embodied on an article of manufacture, e.g., asprocessor-readable instructions stored in a processor-readable storagemedium or be performed as a computer-implemented process. As analternate example, these processes may be encoded asprocessor-executable instructions and transmitted via a communicationsmedium.

FIG. 5 is a diagram illustrating an example dataflow for a process (580)for configuring and using firewalls in ICs. In some examples, process580 may be performed by a master subsystem firewall such as firewall 491and/or firewall 492 of FIG. 4.

In the illustrated example, step 581 occurs first. At step 581, in someexamples, a first firewall is used such that access from a firstsubsystem is blocked upon boot of the device. As shown, step 582 occursnext in some examples. At step 582, the first firewall is enabled to beconfigured by secure code subsequent to boot such that code that is notsecure code is prevented from configuring the first firewall.

As shown, step 583 occurs next in some examples. At step 583, afterconfiguration of the first firewall, upon the first subsystem attemptingto access the first memory, based on the configuration, the firstfirewall is used to selectively allow the first subsystem access to thefirst memory based on ranges of addresses of the first memory configuredas accessible to the first subsystem.

The process may then proceed to the return block, where other processingmay be resumed.

Conclusion

While the above Detailed Description describes certain examples of thetechnology, and describes the best mode contemplated, no matter howdetailed the above appears in text, the technology can be practiced inmany ways. Details may vary in implementation, while still beingencompassed by the technology described herein. As noted above,particular terminology used when describing certain features or aspectsof the technology should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects with which that terminology is associated. Ingeneral, the terms used in the following claims should not be construedto limit the technology to the specific examples disclosed herein,unless the Detailed Description explicitly defines such terms.Accordingly, the actual scope of the technology encompasses not only thedisclosed examples, but also all equivalent ways of practicing orimplementing the technology.

We claim:
 1. An apparatus, comprising: at least one hardware processorconfigured to execute a trusted execution environment and at least oneother execution environment, the trusted execution environment having agreater level of trust than the at least one other executionenvironment; and a first input/output (IO) subsystem that is configuredto control at least some input/output functions for the apparatus,wherein the first IO subsystem includes: a first bus master that isconfigured to operate based on secure code from the trusted executionenvironment; and a first firewall that is configured such thatcommunication from the first IO subsystem to a first range of addressesin a memory mapped address space of the apparatus is blocked from a bootof the apparatus until the first firewall has been configured, and thefirst firewall is further configured to: receive a secure codeconfiguration from the first bus master; in response to receiving thesecure code configuration from the first bus master, configure the firstfirewall with the secure code configuration while code from the at leastone other execution environment is prevented from configuring the firstfirewall; and after the configuring of the first firewall with thesecure code configuration, allow the first IO subsystem to access thefirst range of addresses in the memory mapped address space of theapparatus.
 2. The apparatus of claim 1, further comprising: a second IOsubsystem, wherein the second IO subsystem includes: a second firewallthat is configured such that communication from the second IO subsystemis blocked from the boot of the apparatus until the second firewall hasbeen configured, and the second firewall is further configured to:receive another secure code configuration; in response to receiving theother secure code configuration, configure the second firewall with theother secure code configuration while the code from the at least oneother execution environment is prevented from configuring the secondfirewall; and after the configuring of the second firewall, allow thesecond IO subsystem to access a second range of addresses in the memorymapped address space of the apparatus, wherein at least a portion of thefirst range of addresses in the memory mapped address space of theapparatus does not overlap with the second range of addresses in thememory mapped address space of the apparatus.
 3. The apparatus of claim1, wherein the first range of addresses in the memory mapped addressspace of the apparatus is for at least one of a static random-accessmemory or a flash memory.
 4. The apparatus of claim 1, wherein the firstfirewall is further configured to: after the configuring of the firstfirewall, allow, by the first firewall, the first IO subsystem access toa second range of addresses in the memory mapped address space of theapparatus.
 5. The apparatus of claim 1, wherein the first firewall isfurther configured to: after the configuring of the first firewall,allow, by the first firewall, the first IO subsystem access to a firstperipheral based on a set of peripherals being configured as accessibleto the first IO subsystem.
 6. The apparatus of claim 1, wherein thefirst bus master is further configured to: after the configuring of thefirst firewall, set a sticky lock bit for the first firewall, whereinthe first firewall is further configured to prevent the first firewallfrom being reconfigured after the sticky lock bit for the first firewallis set until a reboot of the apparatus.
 7. A method, comprising:blocking from a boot of the device, with a first configurable firewall,communication from a first input/output (IO) subsystem of the device toa first range of addresses in a memory mapped address space until thefirst configurable firewall has been configured with secure code from atrusted execution environment of the device; subsequent to the boot,configuring the first configurable firewall with the secure code fromthe trusted execution environment of the device while code from at leastone other execution environment of the device is prevented fromconfiguring the first configurable firewall, wherein the trustedexecution environment is associated with a greater level of trust thanthe at least one other execution environment; and after the configuringof the first configurable firewall, selectively allowing the first IOsubsystem access to the first range of addresses in the memory mappedaddress space based on the first range of addresses in the memory mappedaddress space being configured as accessible to the first IO subsystemby the secure code.
 8. The method of claim 7, further comprising:blocking from the boot of the device, with a second configurablefirewall, communication from a second input/output (IO) subsystem of thedevice until the second configurable firewall has been configured;subsequent to the boot, configuring the second configurable firewallwith other secure code from the trusted execution environment of thedevice while code from the at least one other execution environment ofthe device is prevented from configuring the second configurablefirewall; and after the configuring of the second configurable firewall,selectively allowing the second IO subsystem access to a second range ofaddresses in the memory mapped address space based on the second rangeof addresses in the memory mapped address space being configured asaccessible to the second IO subsystem by the other secure code, whereinat least the portion of the first range of addresses in the memorymapped address space does not overlap with the second range of addressesin the memory mapped address space.
 9. The method of claim 7, whereinthe first range of addresses in the memory mapped address space is forat least one of a static random-access memory or a flash memory.
 10. Themethod of claim 7, wherein the first configurable firewall is a hardwarefirewall.
 11. The method of claim 7, wherein the first IO subsystemincludes a microcontroller.
 12. The method of claim 7, furthercomprising: after the configuring of the first configurable firewall,selectively allowing, by the first configurable firewall, the first IOsubsystem access to a second range of addresses in the memory mappedaddress space based on the second range of addresses in the memorymapped address space being configured as accessible to the first IOsubsystem by the secure code.
 13. The method of claim 7, furthercomprising: after the configuring of the first configurable firewall,selectively allowing, by the first configurable firewall, the first IOsubsystem access to a first peripheral based on a set of peripheralsbeing configured as accessible to the first IO subsystem by the securecode.
 14. The method of claim 7, further comprising: after theconfiguring of the first configurable firewall, setting a sticky lockbit for the first configurable firewall, such that after the sticky lockbit is set for the first configurable firewall, the first configurablefirewall is prevented from being reconfigured until a reboot of thedevice.
 15. An apparatus, comprising: at least one hardware processorconfigured to operate in a trusted execution environment; and a firstinput/output (IO) subsystem that is configured to control at least someinput/output functions of the apparatus based on secure code receivedfrom the trusted execution environment, wherein the first IO subsystemincludes: a first hardware firewall that is configured such thatcommunication from the first IO subsystem to a first range of addressesin a memory mapped address space is blocked from a boot of the apparatusuntil the first hardware firewall has been configured, and wherein thefirst hardware firewall is functional to: be configured by the securecode while non-secure code is prevented from configuring the firsthardware firewall; and after configuration of the first hardwarefirewall, selectively allow the first IO subsystem access to the firstrange of addresses in the memory mapped address space based on the firstrange of addresses in the memory mapped address space being configuredas accessible to the first IO subsystem by the configuration.
 16. Theapparatus of claim 15, further comprising: a second IO subsystem, thesecond IO subsystem includes: a second hardware firewall that isconfigured such that communication from the second IO subsystem of theapparatus to a second range of addresses in the memory mapped addressspace is blocked from the boot of the apparatus until the secondhardware firewall has been configured, and wherein the second hardwarefirewall is functional to: be configured by the secure code subsequentto boot while non-secure code is prevented from configuring the secondhardware firewall; and after configuration of the second hardwarefirewall, selectively allow the second IO subsystem access to the secondrange of addresses in the memory mapped address space based on thesecond range of addresses in the memory mapped address space beingconfigured as accessible to the second IO subsystem by theconfiguration, wherein at least the portion of the first range ofaddresses in the memory mapped address space does not overlap with thesecond range of addresses in the memory mapped address space.
 17. Theapparatus of claim 15, wherein the first IO subsystem further includes amicrocontroller.
 18. The apparatus of claim 15, wherein the firsthardware firewall is further functional to: after configuration of thefirst hardware firewall, selectively allow the first IO subsystem accessto a second range of addresses in the memory mapped address space basedon the second range of addresses in the memory mapped address spacebeing configured as accessible to the first IO subsystem by theconfiguration.
 19. The apparatus of claim 15, wherein the first hardwarefirewall is further functional to: after configuration of the firsthardware firewall, selectively allow the first IO subsystem access to afirst peripheral based on a set of peripherals being configured asaccessible to the first 10 subsystem by the configuration.
 20. Theapparatus of claim 15, wherein the first hardware firewall is furtherfunctional to: after configuration of the first hardware firewall,responsive to secure code, set a sticky lock bit for the first hardwarefirewall, such that after the sticky lock bit is set for the firsthardware firewall, the first hardware firewall is prevented from beingreconfigured until reboot.